Release 10.1A: OpenEdge Data Management:
Database Administration

PROSTRCT CREATE qualifier

Creates a void OpenEdge database from a previously defined structure description (.st) file.

prostrct create db-name  [ structure-description-file ]                          [ -blocksize blocksize ]                          [ -validate ]

Parameters

db-name

Specifies the database you want to create.

structure-description-file

Specifies the .st file you want PROSTRCT to access for file information. The default .st file is db-name.st. If you have a structure description file that has the same name as the database you are creating, you do not have to specify structure-description-file. PROSTRCT automatically creates the database from the structure description file that has the same name as your database with the extension .st.

-blocksize blocksize

Specifies the database block size in bytes (for example -blocksize 1024). The maximum number of indexes allowed in a database is based on the database block size. For more information of database limits, see Chapter 2, " OpenEdge RDBMS Limits."

-validate

Parses the contents of the .st file for syntax errors. When -validate is specified, the database is not created. Each line of the structure file is read and evaluated. If errors are detected, the type of error is reported along with the line number. For a discussion of the allowed syntax in a description file, see "Creating a structure description file."

The PROSTRCT CREATE utility allows you to specify the minimum amount of information necessary to create a database. You must specify the area type and extent location. If the extent is fixed length, you must also specify the size. You need not provide specific filename or file extensions. The utility will generate filename and file extensions for all database files according to the following naming convention:

The control area (.db) and the log file (.lg) are placed in the directory specified by the command line dbname parameter.
If a relative pathname is provided, including using common “.” (dot) notation, the relative pathname will be expanded to an absolute pathname. Relative paths begin in your current working directory.
For BI extents, the filename is the database name with a .bn extension, where n represents the number of extents created.
For AI extents, the filename is the database name with a .an extension, where n represents the logical order in which the AI areas will be accessed during normal processing.
For TL extents, the filename is the database name, with a .tn extension.
For Schema area extents, the filename is the database name with a .dn extension, where n represents the order extents were created and will be used.
For application data extents, the filename is the database name and an area number. The area number is a unique identifier that differentiates between different areas. User extent filenames also have a .dn extension, where n represents the order extents were created and will be used.

The newly created database does not contain any metaschema information. Rather, it consists of the database control (DB) area and whatever primary recovery (BI), after-image (AI), two-phase commit transaction log (TL), and application data (.dn) areas you defined in the .st file.

After you create a void database, you must add metaschema information. The OpenEdge RDBMS provides empty databases, each the size of a supported database block size. The empty database and the database you want to copy it to must have the same block size.

Caution: Never use operating system file commands to copy an OpenEdge database. Instead, use the PROCOPY or PRODB utilities.

Notes

You cannot create a database if one already exists with the same name.
See Chapter 14, "Maintaining Database Structure," for more information about the CREATE qualifier with the PROSTRCT utility.